AI_Creation_Events #11754
Merged
AI_Creation_Events #11754
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Machine learning creation event
|
@microsoft-github-policy-service agree |
v-prasadboke
added
Solution
|
Hi @mgstate, the key 'ID' is not present in this analytic rule. Please add it to the rule. You can refer any rule from our repo. Thanks. |
Fixed Entity Mappings and modified kql based on mappings
I see - the appropriate modifications have been made @v-prasadboke @v-shukore |
sorry meant to put @v-shukore |
v-shukore
approved these changes
Feb 5, 2025
v-atulyadav
approved these changes
Feb 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Machine learning creation event
Required items, please complete
Change(s):
Added a new detection rule for Azure Machine Learning Write Operations.
Updated the YAML configuration to include tactics and techniques relevant to potential rogue access or resource creation.
Reason for Change(s):
To monitor and investigate write operations on Azure Machine Learning resources, ensuring that any unauthorized access or resource creation is detected.
Resolves ISSUE #1234 (if applicable).
Version Updated:
Yes
Detections/Analytic Rule templates are required to have the version updated.
Testing Completed:
Yes
The code has been tested in a Microsoft Sentinel environment to validate syntax and execution.
Checked that the validations are passing and have addressed any issues that are present:
Yes